Skip to content

SEO: fix CTR + internal links for "agentic infrastructure" query - #21062

Open
workprentice[bot] wants to merge 2 commits into
masterfrom
seo/agentic-infrastructure-internal-links
Open

SEO: fix CTR + internal links for "agentic infrastructure" query#21062
workprentice[bot] wants to merge 2 commits into
masterfrom
seo/agentic-infrastructure-internal-links

Conversation

@workprentice

@workprentice workprentice Bot commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

Summary

Search Console shows the query "agentic infrastructure" (roughly 1,500 impressions over the trailing 90 days) sitting just outside page one, in the position band where targeted on-page and internal-linking fixes tend to move the needle fastest. On investigation, the on-page basics one would normally check first (title/meta_desc exact-phrase match, an answer-first definition, FAQ schema) turned out to already be fully shipped on /what-is/what-is-agentic-infrastructure/. That page is well-optimized but gets very little of this query's traffic, because almost no internal links point to it with the bare phrase as anchor text, and because the page currently absorbing most of the traffic — /blog/the-agentic-infrastructure-era/ — reads as a dated launch announcement rather than a definition, which likely explains a click-through rate well below what its ranking position would normally earn.

This PR is a small, targeted fix on both fronts rather than a rewrite:

  1. Click-through-rate fix on the incumbent post. content/blog/the-agentic-infrastructure-era/index.md: the meta_desc now leads with the plain definition ("Agentic infrastructure is cloud infrastructure that AI agents provision, govern, and operate through code...") instead of "what we're shipping today," and a one-line orientation link to the what-is page was added right after the <!--more--> break, ahead of Joe Duffy's own copy (untouched otherwise — title is his editorial headline, not an SEO field, and was left alone).
  2. Exact-phrase internal links. Two more posts already use the bare phrase "agentic infrastructure" in prose and now link it to the definitional page: bring-your-terraform-estate-into-the-agentic-era/index.md and why-choose-pulumi-over-terraform/index.md. (Checked every other page using the phrase; several either already link it, use it inside an unlinkable compound like "agentic infrastructure engineer," or only appear in a bolded label — those were left alone rather than forcing an awkward link.)
  3. A real schema defect, fixed at the content level. While auditing the what-is page's rendered FAQPage JSON-LD I found one FAQ entity ("What about infrastructure for AI agents?") whose acceptedAnswer.text had a raw markdown comparison table leaking into it verbatim (|, ---, bold/italic markers). The collector's known any-heading answer-boundary fix (PR schema: any markdown heading terminates a FAQ answer, not just "## " #20841) is already live in master, but a table sitting directly under a question heading with no intervening non-question sub-heading still bleeds through by design. Fixed by shortening that section's direct answer to clean prose and moving the comparison table under a new non-question ### The two meanings compared sub-heading, which the collector always treats as a hard stop. No template change — this is a one-file content restructure, and faq-entity.html itself was left untouched.

Verification

  • Built the page through an isolated Hugo harness (layouts/partials/schema/ + its dependencies + the real content file) and parsed the rendered <script type="application/ld+json"> block directly: FAQPage now has 19 clean mainEntity entries, zero leaked |/#/code-fence characters in any acceptedAnswer.text; the affected entity's answer is now 545 chars of clean prose instead of leaking a raw markdown table.
  • Ran node scripts/lint/lint-markdown.js against all 4 changed files: 0 errors.
  • Confirmed every new/changed link target (/what-is/what-is-agentic-infrastructure/) matches the file's real content slug.
  • Re-read every diff after writing to confirm no indentation/whitespace corruption.
  • Checked PR Add: Platform Engineering in the Agentic Era #20949 ("Add: Platform Engineering in the Agentic Era") — still open/unmerged, so it was not touched here; a follow-up board card tracks adding this page's link there once it merges.

Not in scope here (tracked separately)

  • The faq-entity.html template-level any-heading fix is already shipped (PR schema: any markdown heading terminates a FAQ answer, not just "## " #20841) — verified still present in master, no further template work needed.
  • A GSC re-measurement of this query's CTR/position ~4-6 weeks post-merge is tracked as a follow-up board card; no ranking-movement claims are made in this PR.

🧠 This PR was created by workprentice.

@workprentice
Improve CTR and internal linking for 'agentic infrastructure' query
9b51958 
- Rewrite the-agentic-infrastructure-era meta_desc to lead with the
  answer-first definition (was reading as a dated launch announcement,
  suppressing CTR at position ~6.7 for the query 'agentic infrastructure')
- Add an early orientation link from that post to the definitional
  what-is/what-is-agentic-infrastructure page
- Add exact-phrase internal links from two more blog posts that already
  use the bare phrase 'agentic infrastructure' in prose
- Split a what-is-agentic-infrastructure.md FAQ section so its comparison
  table sits under a non-question sub-heading, preventing raw markdown
  table syntax from leaking into the rendered FAQPage acceptedAnswer text
  (verified via isolated Hugo schema harness: 19 clean FAQ entities, zero
  leaked '|'/'#'/code-fence characters)
@github-actions github-actions Bot added review:triaging Claude Triage is currently classifying the PR domain:docs PR touches technical docs domain:mixed PR touches more than one domain domain:blog PR touches blog posts or customer stories review:in-progress Claude review is currently running and removed review:triaging Claude Triage is currently classifying the PR labels Aug 22, 2026
@github-actions

github-actions Bot commented Aug 22, 2026

Copy link
Copy Markdown
Contributor

Pre-merge Review — Last updated 2026-08-22T00:21:53Z

Tip

Summary: An SEO pass for the "agentic infrastructure" query: three blog posts gain an inline link to /what-is/what-is-agentic-infrastructure/ (one of them also a rewritten meta_desc that leads with the definition), and the what-is page itself is lightly restructured — the "both meanings compound" wrap-up moves ahead of the two-meanings comparison table, which picks up a new ### The two meanings compared heading. The wrongness that would matter here is a link that doesn't resolve, a meta_desc that overpromises or misdefines the term relative to the page it points at, or a reordering that leaves the what-is section reading out of sequence. The link target, the definition wording, and the Terraform-state-backend sentences carrying the new anchors were all checked against the canonical docs and the what-is page; a prose/readthrough pass and pattern-based linting also ran. No blocking issues; one ordering nit noted below.

Review confidence:

Dimension Level Notes
mechanics HIGH
facts HIGH
coherence MEDIUM The what-is reordering is a judgment call — see the ⚠️ note; both readings are defensible.
Investigation log
  • Cross-sibling reads: not run (not in a templated section)
  • External claim verification: 9 of 18 claims verified (0 unverifiable, 0 contradicted) · 4 specialists (numerical, cross-reference, capability, framing); 0 cross-specialist corroborations · routed: 0 inline, 15 Pass 1, 0 Pass 2, 3 Pass 3 (verified 2, contradicted 0, unverifiable 1).
  • Cited-claim spot-checks: not run (no cited claims)
  • Frontmatter sweep: ran on body + meta_desc + social.{bluesky, linkedin, twitter}
  • Temporal-trigger sweep: ran (recency words present in diff; spot-check in-review)
  • Code execution: not run (no static/programs/ change)
  • Code-examples checks: not run (no fenced code blocks in content files)
  • Editorial-balance pass: ran (single-subject, N/A)
🚨 Outstanding ⚠️ Low-confidence 💡 Pre-existing ✅ Resolved
0 1 0 0

🔍 Verification trail

18 claims extracted · 9 verified · 0 unverifiable · 0 contradicted
  • L42 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Pulumi Cloud provides guardrails and enterprise readiness needed to safely move fast in the agentic infrastructure era." → ➖ not-a-claim (evidence: This is a subjective marketing/positioning statement about Pulumi's own product ("Pulumi Cloud provides the guardrails and enterprise readiness needed to safely move fast in this new era") describing the author's own platform value…; source: repo:content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md)
  • L44 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Pulumi is launching three new ways that let users avoid trading off building for the future against building for today, described at…" → ✅ verified (evidence: The blog post's own body states: "Today, we are launching three ways that Pulumi lets you avoid trading off building for the future against building for today," and the post enumerates…; source: repo:content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md; repo:content/blog/terraform-to-pulumi-cloud-hands-on/index.md)
  • L44 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Users do not have to rip out Terraform to adopt Pulumi's agentic infrastructure capabilities." → ✅ verified (evidence: The blog itself documents three GA capabilities—Pulumi Cloud as Terraform state backend, native Terraform module import, and HCL as a first-class Pulumi language—all explicitly designed to work with existing Terraform without rewriting…; source: repo:content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md)
  • L44 in content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md "Pulumi Cloud brings agentic infrastructure capabilities to an existing Terraform-based IaC estate without requiring migration." → ✅ verified (evidence: The blog post itself states: "You don't have to rip out Terraform to enter the agentic era. Pulumi Cloud brings agentic infrastructure to the IaC estate you already have," and the linked release note…; source: repo:content/blog/bring-your-terraform-estate-into-the-agentic-era/index.md and repo:content/releases/terraform-state-backend-modules-hcl.md)
  • L5 in content/blog/the-agentic-infrastructure-era/index.md "Agentic infrastructure is defined as cloud infrastructure that AI agents provision, govern, and operate through code." → ✅ verified (framing: Source: "provision, govern, and operate autonomously, writing code, running deployments, enforcing policy, and proposing changes through pull requests"…; evidence: Pulumi's own "What Is Agentic Infrastructure?" page defines it nearly identically: "Agentic infrastructure is cloud infrastructure that AI agents provision, govern, and operate autonomously, writing code, running deployments, enforcing…; source: https://www.pulumi.com/what-is/what-is-agentic-infrastructure/)
  • L5 in content/blog/the-agentic-infrastructure-era/index.md "Pulumi is building tools/features to make agentic infrastructure real." → ✅ verified (evidence: The Pulumi blog post itself and companion release page describe numerous concrete tools/features (30+ new CLI commands, integration catalog, Scheduled Tasks, Read-Only Sessions, Pulumi Cloud in the CLI) explicitly framed as building…; source: https://www.pulumi.com/releases/agentic-infrastructure-era/ and https://www.pulumi.com/blog/the-agentic-infrastructure-era/)
  • L31 in content/blog/the-agentic-infrastructure-era/index.md "Pulumi has a page at /what-is/what-is-agentic-infrastructure/ that explains what agentic infrastructure is and how it works." → ✅ verified (evidence: content/what-is/what-is-agentic-infrastructure.md exists and renders at /what-is/what-is-agentic-infrastructure/; it defines agentic infrastructure ("cloud infrastructure that AI agents provision, govern, and operate autonomously...")…; source: repo:content/what-is/what-is-agentic-infrastructure.md)
  • L33 in content/blog/the-agentic-infrastructure-era/index.md "Pulumi Neo is described as the agent at the center of the capabilities discussed in the post." → ➖ not-a-claim (evidence: Line 33 of the reviewed post itself states: "Neo is the agent at the center of everything below: it previews changes, checks them against policy, and opens PRs for your review." This is the author's own descriptive framing of their…; source: repo:content/blog/the-agentic-infrastructure-era/index.md)
  • L33 in content/blog/the-agentic-infrastructure-era/index.md "Pulumi Neo is described as the agent at the center of the capabilities discussed in the post." → ➖ not-a-claim (evidence: Line 33 of the reviewed post itself states "Neo is the agent at the center of everything below: it previews changes, checks them against policy, and opens PRs for your review." This is the author's own editorial framing/positioning of…; source: repo:content/blog/the-agentic-infrastructure-era/index.md)
  • L244 in content/blog/why-choose-pulumi-over-terraform/index.md "Teams can keep using the Terraform or OpenTofu CLI for day-to-day operations while using Pulumi Cloud as their Terraform state backend." → ✅ verified (evidence: The canonical docs page states: "Pulumi Cloud can serve as a Terraform state backend... Your team can continue using the Terraform or OpenTofu CLI for day-to-day operations while gaining the benefits of Pulumi Cloud" — this matches the…; source: pulumi/docs:content/docs/iac/get-started/terraform/terraform-state-backend.md)
  • L246 in content/blog/why-choose-pulumi-over-terraform/index.md "Pulumi Cloud uses Terraform's standard remote backend interface, so users can point the Terraform CLI at Pulumi Cloud without changing their infrastructure…" → ✅ verified (evidence: Multiple Pulumi docs pages confirm this: "Pulumi Cloud implements the Terraform remote backend API. You point the Terraform CLI at Pulumi Cloud using the standard backend "remote" configuration block, and no changes to your Terraform…; source: pulumi/docs:content/docs/iac/get-started/terraform/terraform-state-backend.md)
  • L246 in content/blog/why-choose-pulumi-over-terraform/index.md "Users can point the Terraform or OpenTofu CLI at Pulumi Cloud without changing their infrastructure code." → ✅ verified (evidence: Official docs page (content/docs/iac/get-started/terraform/terraform-state-backend.md) states: "Pulumi Cloud can serve as a Terraform state backend... Your team can continue using the Terraform or OpenTofu CLI for day-to-day operations."…; source: pulumi/docs:content/docs/iac/get-started/terraform/terraform-state-backend.md)
  • L87 in content/what-is/what-is-agentic-infrastructure.md "Infrastructure for AI agents and infrastructure managed by AI agents compound, in that agents that understand infrastructure can also manage the…" → ➖ not-a-claim (evidence: This is an editorial/conceptual assertion by the post's author about how two concepts ("infrastructure for AI agents" and "infrastructure managed by AI agents") relate and compound — not a falsifiable technical or product claim checkable…; source: content/what-is/what-is-agentic-infrastructure.md)
  • L87 in content/what-is/what-is-agentic-infrastructure.md "GPU clusters, inference endpoints, vector databases, and RAG pipelines are examples of the platform underneath AI workloads." → ➖ not-a-claim (evidence: This is the author's own conceptual/definitional framing distinguishing "infrastructure for AI agents" from "infrastructure managed by AI agents" — not a third-party factual assertion. The same list (GPU clusters, vector databases…; source: repo:content/what-is/what-is-agentic-infrastructure.md)
  • L94 in content/what-is/what-is-agentic-infrastructure.md "Neo provisions and updates a user's AWS environment as an example of infrastructure managed by AI agents." → ➖ not-a-claim (evidence: Line 94 is a table cell in the document's own comparison table, illustrating "infrastructure managed by AI agents" with a generic example ("Neo provisions and updates your AWS environment"), consistent with the Neo workflow example…; source: repo:content/what-is/what-is-agentic-infrastructure.md)
  • L94 in content/what-is/what-is-agentic-infrastructure.md "A GPU cluster running a training job or inference service is an example of infrastructure for AI agents." → ➖ not-a-claim (evidence: This is an illustrative example within the article's own conceptual table distinguishing 'infrastructure for AI agents' from 'infrastructure managed by AI agents' — a definitional/explanatory device the author is using to illustrate…; source: repo:content/what-is/what-is-agentic-infrastructure.md)
  • L95 in content/what-is/what-is-agentic-infrastructure.md "Infrastructure for AI agents is managed by a platform team, often using infrastructure as code (IaC)." → ➖ not-a-claim (evidence: This is the author's own explanatory/editorial framing in a comparison table ("Your platform team, often using IaC") distinguishing two senses of "agentic infrastructure." It's a general industry description, not a falsifiable, sourced…; source: repo:content/what-is/what-is-agentic-infrastructure.md)
  • L87 in content/what-is/what-is-agentic-infrastructure.md "Reordering: the 'most organizations need both / the two compound' wrap-up now precedes the comparison table that establishes the distinction" → 🤷 unverifiable (evidence: readthrough/ordering judgment rather than a factual assertion — the moved sentences are accurate either way; source: repo:content/what-is/what-is-agentic-infrastructure.md)
  • L97 in content/what-is/what-is-agentic-infrastructure.md "Teams building AI products benefit from AI agents operating that platform, i.e., infrastructure managed by agents." → ➖ not-a-claim (evidence: This is an editorial/positioning statement expressing the author's own thesis about AI agents managing infrastructure, not a falsifiable factual assertion citing an external source or specific data point.; source: content/what-is/what-is-agentic-infrastructure.md (self-authored positioning statement))

📊 Editorial balance

Single-subject post; balance check N/A.

🚨 Outstanding in this PR

No outstanding findings in this PR.

⚠️ Low-confidence

Review each and resolve as appropriate — these don't block the PR.

  • [L87] content/what-is/what-is-agentic-infrastructure.md — the section now states its conclusion before the evidence. The opening paragraph ends with "That is related to, but distinct from, this page's subject… Most organizations need to think about both, and the two compound: agents that understand infrastructure can also manage the infrastructure their own workloads run on." — so by the time the reader reaches ### The two meanings compared, the takeaway has already landed and the table is a recap. The old order (distinction → table → "most organizations will need to think about both") built to it instead. What's left after the table is also a floating pair of sentences with no topic sentence: "Teams building AI products need the platform layer (infrastructure for agents). Those same teams also benefit from AI agents operating that platform (infrastructure managed by agents)." One way to keep the new heading and the tighter intro without the inversion is to leave the compounding sentence below the table, where it can lead the closing paragraph:

    That is related to, but distinct from, this page's subject, which is infrastructure managed by AI agents.

    …and then, after the table:

    Most organizations need to think about both. Teams building AI products need the platform layer (infrastructure for agents), and those same teams also benefit from AI agents operating that platform (infrastructure managed by agents). The two compound: agents that understand infrastructure can also manage the infrastructure their own workloads run on.

    Not blocking — if leading with the conclusion is the deliberate SEO/snippet play here (it does put a quotable summary high on the page), keep it as written.

Style suggestions

Optional polish from pattern-based linting — never blocking, not counted above. Take the ones that read better and ignore the rest. ✏️ marks one you can apply from the Files changed tab — use Add suggestion to batch on each, then Commit suggestions to take several in a single commit.

content/what-is/what-is-agentic-infrastructure.md
  • line 97: [style] wordiness — 'benefit from' is too wordy.

💡 Pre-existing issues in touched files (optional)

No pre-existing issues in touched files.

✅ Resolved since last review

No items resolved since the last review.

📜 Review history

  • 2026-08-22T00:21:53Z — Link target, rewritten meta_desc, and the sentences carrying the new anchors all check out; no blockers, one ⚠️ note on the what-is section's new conclusion-first ordering (9b51958)
  • Refresh this review — comment @claude #update-review. Say what you fixed, or which finding you dispute and why; both work in the same mention.
  • Ask for anything else — comment @claude with no hashtag (questions, one-off fixes). Leaves this review untouched.

Important

Please don't hide, resolve, or delete this comment! It breaks things!

📖 How pre-merge review works — the full lifecycle, short-circuits, and escape hatches.

@github-actions github-actions Bot added review:no-blockers Claude review completed cleanly; outstanding is empty and removed review:in-progress Claude review is currently running labels Aug 22, 2026
@workprentice
Address pre-merge review nit: restore build-to-conclusion order in th…
78a291c 
…e two-meanings section

Move the compounding/conclusion sentence to close the section after the
comparison table instead of before it, per the pre-merge review's
non-blocking readability note. No schema impact: the table remains
under the non-question '### The two meanings compared' sub-heading.
@github-actions github-actions Bot added review:stale New commits since last Claude review; refresh on next ready-transition or @claude mention and removed review:no-blockers Claude review completed cleanly; outstanding is empty labels Aug 22, 2026
@pulumi-bot

pulumi-bot commented Aug 22, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

Your site preview for commit 78a291c is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-21062-78a291c3.s3-website.us-west-2.amazonaws.com

Changed pages:

@workprentice workprentice Bot mentioned this pull request Aug 22, 2026
Merged
workprentice Bot added a commit that referenced this pull request Aug 25, 2026
@workprentice @workprentice
Fix internal links to old /docs/concepts/ URLs (redirect-hop cleanup) (…
1c5c9b5 
…#21072)

* Fix internal links to old /docs/concepts/ URLs (redirect-hop cleanup)

Several docs, blog, and tutorial pages still link to the pre-restructure /docs/concepts/... URLs, which now 301 (some via a double hop) to their current /docs/iac/concepts/..., /docs/esc/concepts/, or /docs/reference/glossary/ locations. Updated 79 files (154 link occurrences, both root-relative markdown links and fully-qualified https://www.pulumi.com/... links) to point directly at the final destination, verified live against the current redirect map. Every fragment (#anchor) and the handful of double-hop cases (missing trailing slash -> slash -> new path) were preserved/collapsed correctly.

One additional file with the same pattern (content/blog/why-choose-pulumi-over-terraform/index.md) was intentionally left untouched because it already has open PRs (#21062, #21066) touching it today; filed a follow-up board card to catch it separately.

* Address pre-merge review: fix stale anchors and mislabeled links

Follow-up to the automated review of the /docs/concepts/ redirect-hop
cleanup. The path rewrites were correct, but several rewritten links kept a
#fragment whose section had moved off the destination page entirely, adding
back a second (client-side JS) redirect hop -- exactly what this PR set out
to remove:

- #components -> /docs/iac/concepts/components/
- #autonaming -> /docs/iac/concepts/resources/names/#autonaming
- #urns -> /docs/iac/concepts/resources/names/#urns
- #dependson -> /docs/iac/concepts/resources/options/dependson/
- #explicit-provider-configuration -> /docs/iac/concepts/providers/
- #additionalsecretoutputs -> /docs/iac/concepts/resources/options/additionalsecretoutputs/
- #transformations -> /docs/iac/concepts/resources/options/transformations/

Applied across all lines in this PR's diff carrying these anchors (verified
each target live), including a couple the review didn't individually cite
but that matched the same pattern.

Also fixed two mislabeled docs-page links flagged by review in
content/docs/iac/guides/migration/import/_index.md: a `retainOnDelete`
mention that pointed at the unrelated `protect` option's page (now points
at its own retainOnDelete page), and a `#autonaming` anchor pointing at the
wrong page (now the names page).

Fixed three "Pulumi Service" (deprecated product name) mentions on lines
this PR already touches, per STYLE-GUIDE.md: keep-your-secrets-secure-by-default,
six-things-about-pulumi-service, and stack-readme now say Pulumi Cloud /
Pulumi Cloud console, and the six-things and keep-your-secrets posts' own
links to the old /product/pulumi-service/ and /docs/pulumi-cloud/self-hosted/
URLs (which themselves redirect) now point directly at their live targets.

Verified: node ./scripts/lint/lint-markdown.js and yarn prettier --check on
all 17 touched files, 0 errors; every new/changed anchor and link target
fetched live to confirm a 200 response before use.

* Address second pre-merge review pass: finish Pulumi Cloud rename, style suggestions

- Finish the Pulumi Service -> Pulumi Cloud rename in
  six-things-about-pulumi-service/index.md (blocker): the prior commit only
  updated the one line the style linter flagged, leaving six more mentions
  and one /product/pulumi-service/ alias hop in the same post.
- Apply 26 of 27 flagged style suggestions across 20 files: punctuation,
  wordiness, filler, weasel words, difficulty qualifiers, spacing, vague
  link text, an unbacked CLI command, and a directional reference.
- Decline one word-choice suggestion (double click -> double select) in
  six-things-about-pulumi-service/index.md as not a real improvement;
  double-click is a named UI gesture with no natural select equivalent.

Verified: yarn prettier --check and node ./scripts/lint/lint-markdown.js
both pass clean on all touched files.

* Fix low-confidence style-edit regressions flagged in third review pass

The 483d4d1 style sweep dropped meaning or grammar in five spots while
clearing linter flags on adjacent words:

- keep-your-secrets-secure-by-default L34: restore the "often" hedge
  ("is enough" -> "is often all you need") so the claim isn't stronger
  than the original and isn't contradicted by the next sentence.
- ai-slack-bot-...-pulumi-on-aws L284: same shape, milder -- restore
  "often" before "happens" for the same reason.
- iac-best-practices-understanding-code-organization-stacks L82: restore
  the coordinating clause the linter's target word was carrying
  ("lightweight to create or delete" -> "lightweight, and creating or
  deleting one is quick").
- next-level-iac-pulumi-runtime-logic L293, L331: restore "immediately"
  before "before the program exits" -- the removed "just" was temporal,
  not a difficulty qualifier, and matches the Node.js/Python docs this
  section quotes.
- six-things-about-pulumi-service L48: fix a pre-existing "such the
  current git SHA" typo (missing "as") while already touching this line
  for the Pulumi Cloud rename.

Verified: yarn prettier --check and node ./scripts/lint/lint-markdown.js
both pass clean on all 5 touched files.

---------

Co-authored-by: workprentice <257153108+workprentice@users.noreply.github.com>
@workprentice workprentice Bot mentioned this pull request Aug 26, 2026
Merged
workprentice Bot pushed a commit that referenced this pull request Aug 26, 2026
@workprentice
Fold in the 3 review-flagged /docs/concepts/ survivors
73e2096 
Fixes the outstanding finding from the pre-merge review:

- content/docs/iac/guides/clouds/aws/eks.md:307 -- a two-line markdown
  link the earlier single-line grep missed; repoints to the canonical
  /docs/iac/concepts/resources/options/transforms/.
- scripts/search/rank.js:80 -- the search-ranking boost for concepts
  pages checked the retired /docs/concepts/ prefix, so it silently
  fell through to the generic docs score (860) instead of 890.
- theme/src/ts/redirects.ts -- "#outputs-and-strings" now lands on
  the section anchor (#using-string-interpolation) instead of the
  top of the page, matching the other 33 entries' precision and the
  stub page's own redirect_to target.

content/blog/why-choose-pulumi-over-terraform/index.md's three
absolute-URL survivors are intentionally left out of this PR: that
file already has two open PRs against it (#21062, #21066) and is
tracked separately.
@workprentice workprentice Bot mentioned this pull request Aug 26, 2026
Merged
CamSoper pushed a commit that referenced this pull request Aug 26, 2026
@workprentice @workprentice
Fix internal links to old /docs/concepts/ URLs missed by #21072 (#21138)
d6fe2dd 
* Fix internal links to old /docs/concepts/ URLs missed by #21072

PR #21072 rewrote 79 files of content/ links from old /docs/concepts/*
to their current /docs/iac/concepts/*, /docs/esc/concepts/*, and
/docs/reference/glossary/* destinations, but its sweep covered content/
markdown links only. Three files outside that scope still pointed at
old dead-hop paths:

- layouts/migrate/terraform.html: a template href, not a content link
- assets/openapi/tag-intros/stacks.md: OpenAPI docs intro fragment
- content/docs/iac/concepts/resources/_index.md: a client-side JS
  hash-redirect map (5 of its 22 entries still pointed at the old
  paths, doing the same job the map exists for but landing on another
  redirect hop instead of the final page)

Each old path was verified against its live redirect chain before
rewriting, confirming the new destination resolves 200 directly:

- /docs/concepts/vs/terraform -> /docs/iac/comparisons/terraform/
- /docs/concepts/stack/ -> /docs/iac/concepts/stacks/
- /docs/concepts/resources/components -> /docs/iac/concepts/components/
- /docs/concepts/resources/names -> /docs/iac/concepts/resources/names/
- /docs/concepts/resources/get -> /docs/iac/concepts/functions/get-functions/

The #urns and #autonaming anchors were confirmed present on the new
resources/names/ page. content/blog/why-choose-pulumi-over-terraform/index.md
is intentionally left untouched here; it is still blocked by open PRs
#21062 and #21066 and is tracked separately.

node ./scripts/lint/lint-markdown.js and ./scripts/prettier.sh --check
both pass on the changed files (the one markdown-lint finding on
assets/openapi/tag-intros/stacks.md is a pre-existing missing-heading
warning on master, unrelated to this change).

---

🧠 *This PR was created by [workprentice](https://github.com/workprentice).*

* Complete redirect-hop cleanup: TS redirect maps, toc.ts, and remaining stale content links

PR #21138 fixed 3 non-content/ surfaces (an asset, the resources hash-redirect
map, and a layout template) but left several sibling defects of the same class:

- theme/src/ts/redirects.ts: a client-side hash-redirect map for the old
  /docs/intro/concepts/programming-model/ page pointed all 34 entries at dead
  /docs/concepts/* hops. Rewrote every entry to its live /docs/iac/concepts/*
  (or /docs/iac/concepts/inputs-outputs/*, /docs/iac/concepts/providers/*, etc.)
  destination, verified 200 with no further hop.
- theme/src/ts/toc.ts: the left-nav active-state map still keyed off the old
  /docs/concepts/ path.
- content/docs/iac/concepts/resources/_index.md: the hash-redirect map added by
  #21138 itself was missing trailing slashes on 16 of its 28 targets, each of
  which 302-redirects to the slashed form -- the same dead-hop defect this
  whole cleanup exists to remove. Added trailing slashes throughout.
- Six remaining content files (archetypes template, two blog posts, the
  insights search reference-link footnotes, and the k8s operator integration
  page) still linked to old /docs/concepts/* paths; rewrote to their current
  /docs/iac/concepts/* destinations.

Every new destination verified live against https://www.pulumi.com with
redirects disabled: all return 200 directly.

A further stale link was found in static-prebuilt/ ESC SDK reference HTML,
but those files are generated from pulumi/esc's own SDK docstrings at build
time, so fixing them here would be overwritten on next regeneration --
tracked separately for a pulumi/esc-side fix.

* Fold in the 3 review-flagged /docs/concepts/ survivors

Fixes the outstanding finding from the pre-merge review:

- content/docs/iac/guides/clouds/aws/eks.md:307 -- a two-line markdown
  link the earlier single-line grep missed; repoints to the canonical
  /docs/iac/concepts/resources/options/transforms/.
- scripts/search/rank.js:80 -- the search-ranking boost for concepts
  pages checked the retired /docs/concepts/ prefix, so it silently
  fell through to the generic docs score (860) instead of 890.
- theme/src/ts/redirects.ts -- "#outputs-and-strings" now lands on
  the section anchor (#using-string-interpolation) instead of the
  top of the page, matching the other 33 entries' precision and the
  stub page's own redirect_to target.

content/blog/why-choose-pulumi-over-terraform/index.md's three
absolute-URL survivors are intentionally left out of this PR: that
file already has two open PRs against it (#21062, #21066) and is
tracked separately.

* Fix crawler-facing meta refresh to skip the /docs/concepts redirect hop

The two retired-URL stub pages (programming-model.md and
programming-model-previous.md) still pointed their meta refresh at
/docs/concepts, which now resolves as a 302-then-301 chain before
landing on /docs/iac/concepts/. Point the refresh straight at the
final destination instead, matching the visible prose link directly
beneath it.

Re-swept current master for the same defect class: the other three
instances found (assets/openapi/tag-intros/stacks.md and the
theme/src/ts/redirects.ts anchor map) are already fixed by this PR's
earlier commits.

* Remove dead /docs/using-pulumi/ ranking branch from search rank.js

Review flagged this as a sibling of the /docs/concepts/ prefix defect this
PR fixes: content/docs/using-pulumi no longer exists, and every remaining
/docs/using-pulumi/... occurrence under content/docs/ is an `aliases:`
entry (a historical redirect source), not a page's own `url:`. No indexed
page's href ever starts with /docs/using-pulumi/, so the branch never
fired -- pages that used to live there now score 860 or 870 via fallthrough,
same as any other docs page.

The content that used to live under /docs/using-pulumi/ moved to three
different trees (iac/, insights/policy/, administration/) with no single
successor prefix, so there's no one replacement string to substitute --
removing the dead branch is the honest fix rather than repointing it.

---------

Co-authored-by: workprentice <257153108+workprentice@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

domain:blog PR touches blog posts or customer stories domain:docs PR touches technical docs domain:mixed PR touches more than one domain review:stale New commits since last Claude review; refresh on next ready-transition or @claude mention

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@pulumi-bot @workprentice